-
Notifications
You must be signed in to change notification settings - Fork 83
Remove notion of v1 and v2 discovery services #1994
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove notion of v1 and v2 discovery services #1994
Conversation
990dbbc to
01eda91
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noticed dbms.kubernetes.service_port_name still referenced.
Co-authored-by: Nick Giles <[email protected]>
Co-authored-by: Nick Giles <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And dbms.kubernetes.discovery.v2.service_port_name is still in configuration-settings.adoc, and I think just needs removing.
Co-authored-by: Nick Giles <[email protected]>
Co-authored-by: Nick Giles <[email protected]>
…very.v2.service_port_name`
|
@jackwaudby, @nick-giles-neo, I found two more pages that need to be freed from mentioning discovery services v2 or v1:
Could you please take a look at them? |
|
@NataliaIvakina I've removed mentions of v1/v2 from those pages. In |
@jackwaudby, you're right, but let's do it in another PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Test failures will be resolved in other PRs.
@nick-giles-neo, any comments?
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
I'm happy! |
Removes all mention of v1 and v2 discovery services. We update all configurations and setup guides to reflect there is now one discovery service with 2 settings:
dbms.cluster.endpointsdbms.cluster.discovery.resolver_type